|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
This is an approved standards track document.
|
|
3.
|
Justification for the specific reference:
|
|
|
This standard is to provide an extensible framework by which SIP nodes can request notification of metadata change.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=3265
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Obsoleted by RFC 6665; Updated by RFC 5727, RFC 5367, RFC 6446; Obsoletes RFC 2543; Updates RFC 3261
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Proposed Standard
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item 8. Updates RFC 2543 and is updated by RFCs 5367, 5727. Errata exist.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
8. Normative References/
/
[1] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A.,/
Peterson, J., Sparks, R., Handley, M. and E. Schooler, "SIP:/
Session Initiation Protocol", RFC 3261, June 2002./
/
[2] Petrack, S. and L. Conroy, "The PINT Service Protocol", RFC/
2848, June 2000./
/
[3] Fielding, R., Gettys, J., Mogul, J., Frystyk, H., Masinter, L.,/
Leach, P. and T. Berners-Lee, "Hypertext Transfer Protocol --/
HTTP/1.1", RFC 2616, June 1999./
/
[4] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA/
Considerations Section in RFCs", BCP 26, RFC 2434, October/
1998./
/
[5] Bradner, S., "Key Words for Use in RFCs to Indicate Requirement/
Levels", BCP 14, RFC 2119, March 1997./
/
[6] Day, M., Aggarwal, S., Mohr, G. and J. Vincent, "Instant/
Messaging/Presence Protocol Requirements", RFC 2779, February/
2000./
/
9. Informative References/
/
[7] Rosenberg, J. and H. Schulzrinne, "Guidelines for Authors of/
SIP Extensions", Work in Progress./
/
[8] Schulzrinne, H. and J. Rosenberg, "SIP Caller Preferences and/
Callee Capabilities", Work in Progress./
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
none
|
|
